[SOLVED] Some Steam games crash X (64-current w/ multilib | 2015.11.25)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
'dwm' does not re-parent top-level windows which sets it aside from many other window-managers (even other tiling ones like i3). Not sure if that is of any significance, but I thought I'd throw it out there as a possible reason for different behaviour.
Since the error looked intel related, I compiled the latest xf86-video-intel (xf86-video-intel-git_20151206_da9ad38-x86_64-1.txz). Same crash and burn when starting 'Spec Ops: The Line'.
There might be a modsetting/modeline problem. It looks like you are using the Display port. How about:
Try another GPU port (VGA, DVI or HDMI)
set up entries /etc/X11/worg.d/<something>.conf to specify driver and valid modes so that X does not try to scan for them
turn off modesetting
Nvidia proprietary drivers don't use the same scheme (no modelines for example), and I specify monitor, driver, and screen parameters in /etc/X11/worg.d/xorg.conf (Old school, that's me...). I have -current on another partition in the game box. I might check 1.18 out here soon
There might be a modsetting/modeline problem. It looks like you are using the Display port. How about:
Try another GPU port (VGA, DVI or HDMI)
set up entries /etc/X11/worg.d/<something>.conf to specify driver and valid modes so that X does not try to scan for them
turn off modesetting
Nvidia proprietary drivers don't use the same scheme (no modelines for example), and I specify monitor, driver, and screen parameters in /etc/X11/worg.d/xorg.conf (Old school, that's me...). I have -current on another partition in the game box. I might check 1.18 out here soon
Interesting, this is a laptop and I am using the built-in display ... how can I disable modesetting?
Wild guess here but I think kingbeowulf means adding "nomodeset" to the append line of your lilo.conf.
Thanks. I'm beginning to believe, after recompiling an older Xorg (1.17.4), that the NVIDIA driver is to blame here, or some kind of broken interaction between Bumblebee and `primusrun`. I'm hoping the next 358.x or 352.x release of the NVIDIA driver will sort things out.
So after rebuilding the entire X11 stack (with updated versions of xf86-video-{intel,nouveau}, and all the latest commits to the xserver 1.18 branch), I've found that everything seems to work in XFCE, but not Fluxbox. WEIRD.
I guess I should test some other DE's and see which ones are 'golden'.
ryan, Keep us posted on your findings. I'm almost done to migrating to -current and will start testing the nvidia blob on -current (and other of my SBo scripts) "real soon now." I'd be interested in and DE quirks with those that Slackware ships.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.